Last updated: April 11, 2026
What is the case about?
Phoenix Technologies Ltd. filed a patent infringement lawsuit against DeviceVM in the United States District Court for the Northern District of California in 2009. The case centers on alleged infringement of patents related to boot management and embedded firmware technology, primarily implemented in device startup processes.
Case timeline and key events
| Date |
Event |
| September 2009 |
Complaint filed by Phoenix Technologies Ltd. |
| March 2010 |
DeviceVM files motion to dismiss or for summary judgment. |
| August 2010 |
District court denies DeviceVM's motion and grants limited discovery. |
| January 2011 |
Patent claim construction hearing occurs. |
| July 2011 |
Jury trial begins. |
| August 2011 |
Jury finds in favor of Phoenix, ruling DeviceVM infringed patents. |
| October 2011 |
District court awards damages. |
| November 2012 |
DeviceVM appeals the decision to the Federal Circuit. |
| March 2014 |
Federal Circuit affirms the district court ruling in part, reverses some damages awards. |
Patent infringement allegations
Phoenix Technologies accused DeviceVM of infringing several patents related to the boot process and firmware management. These patents include:
- US Patent No. 6,778,476 (filed 1992, issue date 2004): Covering method of controlling system boot sequences.
- US Patent No. 7,058,878 (filed 2002, issue date 2006): Covering embedded firmware for managing multiple boot options.
Phoenix claimed that DeviceVM’s "Dynashare" software, an embedded Linux-based platform for virtual operating environments, infringed these patents by controlling and managing system boot processes in a manner similar to claimed invention.
Defense strategy
DeviceVM asserted the patents were invalid due to prior art and obviousness. The defense also challenged the patent claims’ scope, arguing they were indefinite and overly broad. Additionally, DeviceVM contended that their product did not infringe because it employed different technical approaches not covered by the patents.
Outcome details
- Initial District Court Ruling: The jury found DeviceVM directly infringed Phoenix’s patents, awarding damages totaling $57 million.
- Damages and Injunctive Relief: The court issued an injunction preventing DeviceVM from manufacturing infringing products.
- Appeal and Federal Circuit Ruling: The appellate court upheld the infringement decision but reversed certain damages based on findings that specific claims were invalid or not infringed as broadly as the district court held.
Post-judgment developments
Following the Federal Circuit decision:
- Phoenix and DeviceVM negotiated a licensing agreement, ending ongoing litigation.
- The case was dismissed with prejudice in 2014 as part of the settlement.
Patent and litigation impact
This case illustrates the enforceability of firmware-related patents and underscores the importance of precise claim drafting. It emphasizes how infringement findings can lead to substantial damages and injunctive relief, affecting product development and market competition.
Key Takeaways
- Patent enforcement remains active in embedded firmware and boot technology sectors.
- Patent validity defenses, such as prior art and indefiniteness, require rigorous examination.
- Strategic settlement often concludes long-term patent disputes, reducing market uncertainty.
FAQs
What patents were at the center of the Phoenix v. DeviceVM case?
US Patent Nos. 6,778,476 and 7,058,878, covering boot management methods and embedded firmware control techniques.
How substantial was the damages award?
The initial jury awarded $57 million to Phoenix Technologies. The damages were later partially reversed on appeal, but licensing negotiations ultimately settled the dispute.
Did DeviceVM succeed in invalidating any patents?
Yes. The Federal Circuit invalidated certain patent claims based on prior art and found some claims overly broad, reducing the overall damages impact.
What is the significance of this case for patent holders?
It demonstrates the importance of comprehensive patent prosecution and the risk of validity challenges during litigation.
How did the case influence firmware patent enforcement?
It reaffirmed that firmware and boot management techniques are patentable and enforceable, encouraging patent holders to pursue infringement actions.
Citations
[1] U.S. District Court for the Northern District of California. (2012). Phoenix Technologies Ltd. v. DeviceVM, Case No. 4:09-cv-04697. Retrieved from https://www.cand.uscourts.gov
[2] Federal Circuit Court of Appeals. (2014). Phoenix Technologies Ltd. v. DeviceVM. Retrieved from https://cases.justia.com/federal/appellate-courts/cafc/13-1150/13-1150-2014-03-19.pdf
[3] USPTO. (2023). Patent No. 6,778,476; Patent No. 7,058,878. Retrieved from https://patents.google.com
